Cloud-based operator interface for industrial automation

ABSTRACT

A cloud-based operator interface system is provided that runs as a cloud service on a cloud platform. The cloud-based operator interface system collects industrial data from one or more industrial systems via respective cloud gateway devices. A set of predefined operator interface screens are stored on cloud storage associated with the operator interface system, and delivered to authorized Internet-capable client devices upon request. The industrial data received from the cloud gateways can be delivered to the client devices from the cloud platform via the operator interface screens. Additional cloud-side services can correlate and analyzes the industrial data on the cloud platform to facilitate additional reporting, alarming, and notification features.

RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S.patent application Ser. No. 15/278,139, filed on Sep. 28, 2016, andentitled “CLOUD-BASED OPERATOR INTERFACE FOR INDUSTRIAL AUTOMATION,”which is a continuation of U.S. patent application Ser. No. 13/608,821,filed on Sep. 10, 2012, which claims the benefit of U.S. ProvisionalPatent Application Ser. No. 61/587,531, filed on Feb. 9, 2012, andentitled “INDUSTRIAL AUTOMATION CLOUD COMPUTING SYSTEMS AND METHODS,”and U.S. Provisional Patent Application Ser. No. 61/642,964, filed May4, 2012, and entitled “CLOUD GATEWAY FOR INDUSTRIAL AUTOMATIONINFORMATION.” This application is also related to U.S. patentapplication Ser. No. 10/162,315, filed on Jun. 4, 2002 (which issued asU.S. Pat. No. 7,151,966 on Dec. 19, 2006), and entitled “SYSTEM ANDMETHODOLGY PROVIDING OPEN INTERFACE AND DISTRIBUTED PROCESSING IN ANINDUSTIRAL CONTROLLER ENVIRONMENT.” The entireties of these applicationsare incorporated herein by reference.

TECHNICAL FIELD

The subject application relates generally to industrial automation, and,more particularly, to a cloud-based operator interface system for remotemonitoring and control of industrial systems.

BACKGROUND

Industrial controllers and their associated I/O devices are central tothe operation of modern automation systems. These controllers interactwith field devices on the plant floor to control automated processesrelating to such objectives as product manufacture, material handling,batch processing, supervisory control, and other such applications.Industrial controllers store and execute user-defined control programsto effect decision-making in connection with the controlled process.Such programs can include, but are not limited to, ladder logic,sequential function charts, function block diagrams, structured text, orother such platforms.

Industrial automation systems often include one or more operatorinterfaces that allow plant personnel to view telemetry and status dataassociated with the automation system, and to control some aspects ofsystem operation. These operator interfaces typically execute oncomputers that are networked to one or more industrial controllers usedto control the automation system, and render selected subsets of dataread from the controllers in animated graphical or text formats onpre-developed display screens. Operator interfaces can be used tomonitor such information as production statistics, real-time telemetrydata (e.g., temperatures, pressures, flow rates, motor speeds, etc.),machine modes and statuses, alarm conditions, or other such metrics ofthe automation system being monitored.

Since industrial operator interfaces require access to data within theindustrial controllers, and therefore must share a common network withthe industrial controllers, such operator interface systems areconventionally located in proximity to the automation system beingmonitored. Consequently, industrial data and statuses can only be viewedby personnel in proximity to the automation system (e.g., on the plantfloor). Moreover, the data available to such operator interfaces islimited to data stored in controllers sharing a common network with theoperator interface terminal.

The above-described deficiencies of today's industrial control systemsare merely intended to provide an overview of some of the problems ofconventional systems, and are not intended to be exhaustive. Otherproblems with conventional systems and corresponding benefits of thevarious non-limiting embodiments described herein may become furtherapparent upon review of the following description.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects described herein. This summary is not anextensive overview nor is intended to identify key/critical elements orto delineate the scope of the various aspects described herein. Its solepurpose is to present some concepts in a simplified form as a prelude tothe more detailed description that is presented later.

One or more embodiments of the present disclosure relate to acloud-based operator interface system that allows an industrial systemto be monitored and/or controlled remotely via a cloud platform. To thisend, an operator interface system running as a service on a cloudplatform can receive industrial data from one or more industrialautomation systems, and render the industrial data on selectedInternet-capable devices via customized operator interface screensserved to the devices from the cloud platform. The industrial data canbe provided to the cloud-based operator interface system using one ormore cloud gateways located at the respective industrial systems. Thecloud gateways can gather data from the industrial controllersassociated with a given industrial system and push the data to acustomer-specific operator interface system residing on the cloudplatform. In this manner, the cloud-based operator interface system cancollect data from multiple industrial systems at different geographiclocations, and store, filter, associate, correlate, and/or aggregate thecollected data in meaningful ways according to the needs of the user.The operator interface system can generate displays screens forrendering selected subsets of the collected data, and deliver thedisplays to Internet-capable display devices via the Internet. Thus, thecloud-based operator interface system can allow authorized users toremotely monitor multiple industrial automation systems through anysuitable computing device having access to the Internet (e.g., phone,desktop computer, laptop computer, tablet computer, etc.).

One or more embodiments of the cloud-based operator interface system canalso support event-based notification of critical system events. In suchembodiments, the cloud-based operator interface system can be configuredto recognize critical events relating to one or more monitoredindustrial systems (e.g., a system parameter exceeding a setpoint value,a particular machine status, a machine or system alarm condition, etc.),and each defined event can be associated with a list of relevantpersonnel to be notified in response to occurrence of the defined event.When the operator interface system determines that a notification eventhas occurred (e.g., an event at one of the monitored industrial systemsor an aggregate status based on aggregated data from multiple industrialsystems), the operator interface system can deliver notifications of theevent to devices associated with the relevant personnel.

The cloud-based operator interface system can also contextualizeindustrial data received from the various industrial systems to enhancethe value of the information presented to the user. This can includetagging the data with contextual metadata, such as a time, a location, aproduction area, a machine or process state, personnel identifications,or other information that provides additional context for the data. Thisappended contextual data can be leveraged in connection withaggregating, filtering, or summarizing the data on the cloud platform tofacilitate flexible and meaningful presentation of the data to theclient devices.

To the accomplishment of the foregoing and related ends, certainillustrative aspects are described herein in connection with thefollowing description and the annexed drawings. These aspects areindicative of various ways which can be practiced, all of which areintended to be covered herein. Other advantages and novel features maybecome apparent from the following detailed description when consideredin conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high-level overview of an industrial enterprise thatleverages cloud-based services.

FIG. 2 is a block diagram of an exemplary cloud-based operator interfacesystem that collects and provisions industrial data via a cloudplatform.

FIG. 3 is a high-level overview of a cloud-based operator interfacesystem that collects and aggregates data from multiple industrialsystems and visualizes the data on Internet-capable client devices.

FIG. 4 illustrates a high level architecture of a cloud gatewayapplication that uploads data from a controller to an associated cloudapplication.

FIG. 5 is a block diagram illustrating components of an exemplarycloud-based operator interface system.

FIG. 6 illustrates an exemplary context component for transforming rawindustrial data into contextualized data.

FIG. 7 is a block diagram of an exemplary cloud-based notificationarchitecture.

FIG. 8 is a flowchart of an example methodology for viewing andcontrolling one or more industrial systems through a cloud platform.

FIG. 9 is a flowchart of an example methodology for deliveringnotifications of industrial events through a cloud platform.

FIG. 10 is a flowchart of an example methodology for delivering operatorinterface display screens to Internet-capable client devices from acloud platform.

FIG. 11 is an example computing environment.

FIG. 12 is an example networking environment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding thereof. It may be evident, however, that the subjectdisclosure can be practiced without these specific details. In otherinstances, well-known structures and devices are shown in block diagramform in order to facilitate a description thereof.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “controller,” “terminal,” “station,” “node,”“interface” are intended to refer to a computer-related entity or anentity related to, or that is part of, an operational apparatus with oneor more specific functionalities, wherein such entities can be eitherhardware, a combination of hardware and software, software, or softwarein execution. For example, a component can be, but is not limited tobeing, a process running on a processor, a processor, a hard disk drive,multiple storage drives (of optical or magnetic storage medium)including affixed (e.g., screwed or bolted) or removably affixedsolid-state storage drives; an object; an executable; a thread ofexecution; a computer-executable program, and/or a computer. By way ofillustration, both an application running on a server and the server canbe a component. One or more components can reside within a processand/or thread of execution, and a component can be localized on onecomputer and/or distributed between two or more computers. Also,components as described herein can execute from various computerreadable storage media having various data structures stored thereon.The components may communicate via local and/or remote processes such asin accordance with a signal having one or more data packets (e.g., datafrom one component interacting with another component in a local system,distributed system, and/or across a network such as the Internet withother systems via the signal). As another example, a component can be anapparatus with specific functionality provided by mechanical partsoperated by electric or electronic circuitry which is operated by asoftware or a firmware application executed by a processor, wherein theprocessor can be internal or external to the apparatus and executes atleast a part of the software or firmware application. As yet anotherexample, a component can be an apparatus that provides specificfunctionality through electronic components without mechanical parts,the electronic components can include a processor therein to executesoftware or firmware that provides at least in part the functionality ofthe electronic components. As further yet another example, interface(s)can include input/output (I/O) components as well as associatedprocessor, application, or Application Programming Interface (API)components. While the foregoing examples are directed to aspects of acomponent, the exemplified aspects or features also apply to a system,platform, interface, layer, controller, terminal, and the like.

As used herein, the terms “to infer” and “inference” refer generally tothe process of reasoning about or inferring states of the system,environment, and/or user from a set of observations as captured viaevents and/or data. Inference can be employed to identify a specificcontext or action, or can generate a probability distribution overstates, for example. The inference can be probabilistic—that is, thecomputation of a probability distribution over states of interest basedon a consideration of data and events. Inference can also refer totechniques employed for composing higher-level events from a set ofevents and/or data. Such inference results in the construction of newevents or actions from a set of observed events and/or stored eventdata, whether or not the events are correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom the context, the phrase “X employs A or B” is intended to mean anyof the natural inclusive permutations. That is, the phrase “X employs Aor B” is satisfied by any of the following instances: X employs A; Xemploys B; or X employs both A and B. In addition, the articles “a” and“an” as used in this application and the appended claims shouldgenerally be construed to mean “one or more” unless specified otherwiseor clear from the context to be directed to a singular form.

Furthermore, the term “set” as employed herein excludes the empty set;e.g., the set with no elements therein. Thus, a “set” in the subjectdisclosure includes one or more elements or entities. As anillustration, a set of controllers includes one or more controllers; aset of data resources includes one or more data resources; etc.Likewise, the term “group” as utilized herein refers to a collection ofone or more entities; e.g., a group of nodes refers to one or morenodes.

Various aspects or features will be presented in terms of systems thatmay include a number of devices, components, modules, and the like. Itis to be understood and appreciated that the various systems may includeadditional devices, components, modules, etc. and/or may not include allof the devices, components, modules etc. discussed in connection withthe figures. A combination of these approaches also can be used.

FIG. 1 illustrates a high-level overview of an industrial enterprisethat leverages cloud-based services. The enterprise comprises one ormore industrial facilities 104, each having a number of industrialdevices 108 and 110 in use. The industrial devices 108 and 110 can makeup one or more automation systems operating within the respectivefacilities 104. Exemplary automation systems can include, but are notlimited to, batch control systems (e.g., mixing systems), continuouscontrol systems (e.g., PID control systems), or discrete controlsystems. Industrial devices 108 and 110 can include such devices asindustrial controllers (e.g., programmable logic controllers or othertypes of programmable automation controllers); field devices such assensors and meters; motor drives; operator interfaces (e.g.,human-machine interfaces, industrial monitors, graphic terminals,message displays, etc.); industrial robots, barcode markers and readers;vision system devices (e.g., vision cameras); smart welders; or othersuch industrial devices.

Exemplary automation systems can include one or more industrialcontrollers that facilitate monitoring and control of their respectiveprocesses. The controllers exchange data with the field devices usingnative hardwired I/O or via a plant network such as Ethernet/IP, DataHighway Plus, ControlNet, Devicenet, or the like. A given controllertypically receives any combination of digital or analog signals from thefield devices indicating a current state of the devices and theirassociated processes (e.g., temperature, position, part presence orabsence, fluid level, etc.), and executes a user-defined control programthat performs automated decision-making for the controlled processesbased on the received signals. The controller then outputs appropriatedigital and/or analog control signaling to the field devices inaccordance with the decisions made by the control program. These outputscan include device actuation signals, temperature or position controlsignals, operational commands to a machining or material handling robot,mixer control signals, motion control signals, and the like. The controlprogram can comprise any suitable type of code used to process inputsignals read into the controller and to control output signals generatedby the controller, including but not limited to ladder logic, sequentialfunction charts, function block diagrams, structured text, or other suchplatforms.

Although the exemplary overview illustrated in FIG. 1 depicts theindustrial devices 108 and 110 as residing in fixed-location industrialfacilities 104, the industrial devices 108 and 110 may also be part of amobile control application, such as a system contained in a truck orother service vehicle.

According to one or more embodiments of this disclosure, industrialdevices 108 and 110 can be coupled to a cloud platform 102 in order toleverage cloud-based applications. That is, the industrial device 108and 110 can be configured to discover and interact with cloud-basedcomputing services 112 hosted by cloud platform 102. Cloud platform 102can be any infrastructure that allows computing services 112 to beaccessed and utilized by cloud-capable devices. Cloud platform 102 canbe a public cloud accessible via the Internet by devices having Internetconnectivity and appropriate authorizations to utilize the services 112.In some scenarios, cloud platform 102 can be provided by a cloudprovider as a platform-as-a-service (PaaS), and the services 112 (suchas the operator interface system described herein) can reside andexecute on the cloud platform 102 as a cloud-based service. In some suchconfigurations, access to the cloud platform 102 and the services 112can be provided to customers as a subscription service by an owner ofthe services 112. Alternatively, cloud 102 can be a private cloudoperated internally by the enterprise. An exemplary private cloud cancomprise a set of servers hosting the cloud services 112 and residing ona corporate network protected by a firewall.

Cloud services 112 can include, but are not limited to, data storage,data analysis, control applications (e.g., applications that cangenerate and deliver control instructions to industrial devices 108 and110 based on analysis of near real-time system data or other factors),visualization applications such as the cloud-based operator interfacesystem described herein, reporting applications, Enterprise ResourcePlanning (ERP) applications, notification services, or other suchapplications. If cloud platform 102 is a web-based cloud, industrialdevices 108 and 110 at the respective industrial facilities 104 mayinteract with cloud services 112 directly or via the Internet. In anexemplary configuration, industrial devices 108 and 110 may access thecloud services 112 through separate cloud gateways 106 at the respectiveindustrial facilities 104, where the industrial devices 108 and 110connect to the cloud gateways 106 through a physical or wireless localarea network or radio link. In another exemplary configuration, theindustrial devices may access the cloud platform directly using anintegrated cloud interface.

Providing industrial devices with cloud capability can offer a number ofadvantages particular to industrial automation. For one, cloud-basedstorage offered by the cloud platform can be easily scaled toaccommodate the large quantities of data generated daily by anindustrial enterprise. Moreover, multiple industrial facilities atdifferent geographical locations can migrate their respective automationdata to the cloud for aggregation, collation, collective analysis, andenterprise-level reporting without the need to establish a privatenetwork between the facilities. Industrial devices 108 and 110 havingsmart configuration capability can be configured to automatically detectand communicate with the cloud platform 102 upon installation at anyfacility, simplifying integration with existing cloud-based datastorage, analysis, or reporting applications used by the enterprise. Inanother exemplary application, cloud-based diagnostic applications canmonitor the health of respective automation systems or their associatedindustrial devices across an entire plant, or across multiple industrialfacilities that make up an enterprise. Cloud-based lot controlapplications can be used to track a unit of product through its stagesof production and collect production data for each unit as it passesthrough each stage (e.g., barcode identifier, production statistics foreach stage of production, quality test data, abnormal flags, etc.).These industrial cloud-computing applications are only intended to beexemplary, and the systems and methods described herein are not limitedto these particular applications. The cloud platform 102 can allowbuilders of industrial applications to provide scalable solutions as aservice, removing the burden of maintenance, upgrading, and backup ofthe underlying infrastructure and framework.

FIG. 2 is a block diagram of an exemplary cloud-based operator interfacesystem that can be used to collect and provision industrial data via acloud platform. Aspects of the systems, apparatuses, or processesexplained in this disclosure can constitute machine-executablecomponents embodied within machine(s), e.g., embodied in one or morecomputer-readable mediums (or media) associated with one or moremachines. Such components, when executed by one or more machines, e.g.,computer(s), computing device(s), automation device(s), virtualmachine(s), etc., can cause the machine(s) to perform the operationsdescribed.

Cloud-based operator interface system 202 can include a gatewayinterface component 204, a client interface component 206, a contextcomponent 208, an analytics component 210, a notification component 212,one or more processors 214, and memory 216. In various embodiments, oneor more of the gateway interface component 204, client interfacecomponent 206, context component 208, analytics component 210,notification component 212, one or more processors 214, and memory 216can be electrically and/or communicatively coupled to one another toperform one or more of the functions of the cloud-based operatorinterface system 202. In some embodiments, components 204, 206, 208,210, and 212 can comprise software instructions stored on memory 216 andexecuted by processor(s) 214. The cloud-based operator interface system202 may also interact with other hardware and/or software components notdepicted in FIG. 2. For example, processor(s) 214 may interact with oneor more external user interface devices, such as a keyboard, a mouse, adisplay monitor, a touchscreen, or other such interface devices.

Gateway interface component 204 can be configured to receive industrialdata sent by one or more cloud gateways at respective industrialsystems. Client interface component 206 can be configured to deliverpre-configured display screens to remote devices having Internetconnectivity, and to render selected subsets of the collected industrialdata via the display screens. Context component 208 can be configured toappend contextual information to data received by the gateway interfacecomponent 204. This contextual information can include, but is notlimited to, a time/date stamp, a location associated with the data(e.g., a geographical location, a production area, etc.), machinestatuses at the time the data was generated, a lot number, or other suchcontextual information.

Analytics component 210 can be configured to analyze the receivedindustrial data according to predefined criteria. For example, theanalytics component 210 can analyzed incoming industrial datasubstantially in real-time to determine whether a predefined eventrelating to an industrial system (or an aggregation of disparateindustrial systems) has been met, for the purpose of generating anddelivering alarm indications or notifications to selected devices.Notification component 212 can be configured to deliver suchnotifications to the selected devices according to predefined userpreferences. The one or more processors 214 can perform one or more ofthe functions described herein with reference to the systems and/ormethods disclosed. Memory 216 can be a computer-readable storage mediumstoring computer-executable instructions and/or information forperforming the functions described herein with reference to the systemsand/or methods disclosed. In some embodiments, memory 216 can becloud-based storage provided by the cloud platform that maintains andexecutes the cloud-based operator interface system 202.

FIG. 3 illustrates a high-level overview of a cloud-based operatorinterface system that collects and aggregates data from multipleindustrial systems and visualizes the data on Internet-capable clientdevices. Embodiments of the cloud-based operator interface systemdescribed herein can interact with suitable client devices to implementsubstantially any type of industrial operator interface system,including but not limited to human-machine interfaces (HMIs), graphicterminal systems, industrial monitors, message display systems, or othersuch operator interface applications. Accordingly, the term “operatorinterface” as used throughout this disclosure is to be understood toencompass all such industrial display systems.

Cloud-based operator interface system 306 resides on a cloud platform(similar to cloud platform 102 of FIG. 1). Industrial systems 312 ₁-312_(N) use respective cloud gateways 310 ₁-310 _(N) to push industrialdata relating to the industrial systems 312 ₁-312 _(N) to the cloudplatform for collection and processing at the cloud-based operatorinterface system 306. Industrial systems 312 ₁-312 _(N) may be, forexample, automation systems located at respective manufacturing orprocessing facilities. One or more of the industrial systems 312 ₁-312_(N) may also be mobile systems (e.g., systems embedded in service orcargo vehicles) that are to be monitored and/or controlled regardless oftheir location. In some exemplary scenarios, the industrial systems 312₁-312 _(N) will belong to a common industrial enterprise or business,and the cloud-based operator interface system 306 can be made availableto the enterprise as a subscription service. In other exemplaryscenarios, cloud-based operator interface system 306 may provide remoteoperator interface and visualization services to multiple customers. Insuch cases, industrial systems 312 ₁-312 _(N) may belong to multipledifferent equipment owners or businesses.

In some embodiments, the cloud gateways 310 ₁-310 _(N) can gather thedata from one or more industrial controllers that monitor and controlportions of the industrial systems 312 ₁-312 _(N), and push thecontroller data to the cloud platform via web services exposed by acloud application. Also, in some applications, the cloud gateways 310₁-310 _(N), the industrial controllers, or other industrial devicescomprising the industrial systems 312 ₁-312 _(N) may transform the rawindustrial data prior to upload to a format better suited to cloud-basedstorage, computing, or analysis. For example, the cloud gateways 310₁-310 _(N) may filter, prune, re-format, aggregate, summarize, orcompress the raw industrial data to more efficiently utilize cloudbandwidth and/or storage resources. Alternatively, the cloud gateways310 ₁-310 _(N) may upload the raw industrial data to the cloud platformwithout applying additional transformations to the data.

The cloud-based operator interface system 306 receives the industrialdata from the multiple industrial systems 312 ₁-312 _(N) and makes thedata available to client devices 302 ₁-302 _(N) associated with usershaving appropriate access privileges to the data. If the industrial datais to be stored for historian or reporting purposes, the cloud-basedoperator interface system 306 can store the data on cloud-based storageassociated with the cloud platform. The client devices 302 ₁-302 _(N)access the cloud-based operator interface system 306 through a genericInternet level. To facilitate viewing of the industrial data,cloud-based operator interface system 306 can serve display screens tothe client devices 302 ₁-302 _(N) that can be viewed using the devices'native display capabilities. The display screens can be preconfigured byan administrator of the cloud-based operator interface system 306,although some embodiments can allow the owners of the client devices 302₁-302 _(N) to customize the way the industrial data is presented on therespective devices. Client devices 302 ₁-302 _(N) can be personal devicesuch as mobile phones having graphical display capabilities, desktop orlaptop computers, tablet computers, or other such devices. Clientdevices 302 ₁-302 _(N) may also be industrial display devices such asHMI display terminals, graphic terminals, industrial monitors, messagedisplays, television monitors, or the like.

In one or more embodiments, the cloud-based operator interface system306 can apply cloud-side processing to the industrial data to facilitatepresenting the data in meaningful ways to the client devices 302 ₁-302_(N). For example, cloud-based operator interface system 306 can addcontext to the incoming data (e.g., a time/date stamp, a locationassociated with the data, machine statuses at the time the data wasgenerated, etc.). The cloud-based operator interface system 306 may alsoaggregate data from multiple industrial systems 312 ₁-312 _(N) accordingto predefined aggregation rules defined by the user. Using these toolsin the context of a cloud-based operator interface system, data frommultiple, geographically diverse industrial systems can be collected,correlated, and aggregated to generate unified enterprise-levelpresentations of the industrial systems as a whole.

FIG. 4 illustrates a high level architecture of a cloud gatewayapplication that can be used to upload data from a controller to a cloudapplication, such as a cloud-based operator interface system. The majorlayers are the generic Internet 402, the cloud platform 406, and theindustrial equipment 408 comprising an industrial system. Industrialequipment 408 can be, for example, an industrial system comprising anumber of industrial devices 412 ₁-412 _(N) being monitored and/orcontrolled by an industrial controller 410. Industrial equipment 408 canalso comprise higher level systems, such as on-premise data historians(including site-level historians or machine-level historians),supervisory control systems, batch systems, business intelligencesystems, or other business-level or enterprise-level systems. Industrialequipment 408 can have a fixed location (e.g., an industrial facility),or can be a mobile system (e.g., a controlled system loaded on a serviceor cargo vehicle). A cloud gateway 404 can be used to periodically orcontinuously upload data from the controller 410 to one or more cloudapplications on cloud platform 406, such as a cloud-based operatorinterface system, cloud-based storage, cloud-side processing services,or other cloud-based services. Cloud gateway 404 can access cloudplatform 406, for example, via a generic internet layer 402.

In an exemplary scenario, cloud platform 406 can comprise a set of cloudresources provisioned to a provider of cloud services 414 as aplatform-as-a-service (Paas), and the cloud services 414 (such as theoperator interface system described herein) can reside and execute onthe cloud platform 406 as cloud-based services.

Cloud applications such as the cloud-based operator interface system andassociated cloud services described herein can be built on the cloudplatform 406. In one or more embodiments, the cloud platform 406 can becompatible with data models that are developed for enhancedmanufacturing intelligence (EMI) software. Such applications can collectdata from a customer's industrial system and correlate the data for thepurpose of generating reports, creating custom visualizations, archivingthe data, performing system analyses, or other functions. The cloudservices 414 can support federated security, which provides securedaccess to the cloud services from smart devices, such as phones andtablet computers.

The cloud services 414 can deliver visibility, reporting, analytics, andevent management via clients 416, which can interface with the cloudservices 414 via the generic Internet layer 402. To cater for smartdevices such as smart phones and tablet PCs, some cloud services 414 maynot leverage flash-based dashboards, which often cannot be rendered onsome mobile devices. Instead, some cloud services 414 may includedashboards built based on HyperText Markup Language (HTML) and/orJavaScript technology. Internally, such dashboards may use a set of JSON(JavaScript Object Notation) based web services that are optimized forconsumption by HTML/Javascript components. The foregoing should beunderstood as a concrete example and does not exclude the use of otherappropriate technologies for communicating data to the client anddisplaying data on client devices.

The cloud gateway 404 can be any suitable device capable of gatheringdata from controller 410 or other industrial equipment, and pushing thedata to the cloud applications on cloud platform 406. The cloud gateway404 can be a stand-alone device, such as a computer running cloudgateway services and sharing a network with the controller 410.Alternatively, the cloud gateway 404 can be embedded in the controller410 or other piece of industrial equipment. In some embodiments, thecloud gateway 404 may also be integrated within a network interfacedevice, such as a hub, switch, router, or firewall box, residing on acommon network with controller 410. The cloud gateway 404 can include aservice responsible for pushing controller data from the controller 410into cloud-based storage on cloud platform 406 via web services exposedby one or more cloud applications (e.g., the cloud-based operatorinterface system). One or more embodiments of the cloud gateway 404 cansupport store-and-forward logic that causes controller data to beuploaded to the cloud platform 406 to be temporarily stored locally onthe gateway 404 in the event that the connection between the gateway 404and the cloud platform 406 is disrupted. Any suitable communicationtechnology can be used to facilitate communication between the cloudgateway 404 and the cloud platform 406, including but not limited towireless radio (e.g., 3G, 4G, etc.).

In addition to sending controller data to cloud-based applications oncloud platform 406, the cloud gateway 404 can also receive configurationinstructions from the cloud-based applications. For example, acloud-based application (such as the cloud-based operator interfacesystem described herein) can send an instruction informing the gateway404 how frequently data should be uploaded to the cloud-basedapplication (e.g., every minute, every 15 minutes, etc.). The cloudgateway 404 can also be configured locally using a stored configurationdata that holds such information as a system identifier (e.g.,identification of the industrial system monitored by the cloud gateway404), a controller identifier of controller 410, a list of controllertags whose values are to be read by the gateway 404 and uploaded to thecloud-based application, a uniform resource locator (URL) of thecloud-based application, a maximum amount of data to store locally atthe cloud gateway 404 in the event of communication loss between thegateway 404 and the cloud platform 406, or other such configurationinformation.

FIG. 5 is a block diagram illustrating components of an exemplarycloud-based operator interface system. As described in previousexamples, cloud-based operator interface system 502 can reside on acloud platform and receive industrial data from respective cloudgateways 504 (similar to cloud gateways 310 and 404 of FIGS. 3 and 4,respectively). In one or more embodiments, the cloud-based operatorinterface system 502 can reside and execute on the cloud platform as acloud-based service, and access to the cloud platform and operatorinterface system 502 can be provided to customers (e.g., owners of theindustrial systems to be monitored and controlled via the cloud basedoperator interface system 502) as a subscription service by a providerof the services associated with the cloud-based operator interfacesystem 502.

The cloud gateways 504 can retrieve data from respective fixed or mobileindustrial systems (e.g., from one or more industrial controllers thatmonitor and control the respective industrial systems) and send theretrieved data to the cloud-based operator interface system 502. Thecloud gateways 504 can reside at different locations (e.g., locations1-3 of FIG. 5). For example, some cloud gateways 504 can be associatedwith respective automation systems at geographically diverse industrialfacilities, or at different areas within the same facility which may ormay not reside on a common local area network. Some cloud gateways 504may also be embedded within mobile systems, such as service vehicles orcargo trucks having built-in control systems or tracking systems.

The cloud gateways 504 can send their respective industrial data to thecloud-based operator interface system 502 at a frequency defined by theoperator interface system 502. For example, an administrator of thecloud-based operator interface system 502 can define an upload frequencyindividually for the respective cloud gateways 504, and the gatewayinterface component 524 can provide corresponding configurationinstructions to the respective cloud gateways 504 configuring the uploadfrequencies accordingly. Alternatively or in addition, the cloud-basedoperator interface system 502 may dynamically select a suitable uploadfrequency for the respective cloud gateways 504 during operation. Forexample, in order to control costs associated with cloud resourceutilization, an administrator of the cloud-based operator interfacesystem can, in one or more embodiments, configure a maximum totalbandwidth usage for the cloud-based operator interface system 502, suchthat the total instantaneous bandwidth usage for data traffic betweenthe cloud gateways 504 and the cloud-based operator interface system 502is not to exceed the configured maximum bandwidth. In such embodiments,the cloud-based operator interface system 502 can monitor the totalbandwidth utilization substantially in real-time, and dynamically reducethe upload frequency of one or more cloud gateways 504 in response to adetermination that the total bandwidth usage is approaching the definedmaximum bandwidth. In another example, an administrator can configure alimit on the total amount of cloud storage to be used for historicaldata collection. Accordingly, if the cloud-based operator interfacesystem 502 determines that this storage limit is being approached, theoperator interface system 502 can send an instruction to one or morecloud gateways 504 to reduce their upload frequencies, thereby slowingthe consumption of cloud storage resources. The cloud-based operatorinterface system 502 can select which cloud gateways 504 are to beadjusted based on respective criticalities of the control systemsassociated with the cloud gateways 504. For example, cloud-basedoperator interface system 502 can maintain individual gateway profiles(not shown) defining relative priorities of the industrial systemsassociated with each cloud gateway 504, and can leverage thisinformation in connection with determining which cloud gateways 504 areto be selected for reduced upload frequency in the event that one ormore cloud resources are being used at an excessive rate.

The industrial data from the cloud gateways 504 are received at gatewayinterface component 524, which can store the received data on cloudstorage 506 (if the data is to be archived for later viewing), or passthe data directly to client interface component 512 for delivery to anInternet capable client device 520 to facilitate substantially (near)real-time monitoring of the industrial data. Cloud storage 506 cancomprise a subset of the cloud platform's storage resources provisionedto an owner of the industrial systems (e.g., an industrial enterprise)for the purpose of storing the received industrial data. For example,cloud storage 506 can be provided to an industrial enterprise as part ofa subscription service that includes access to the cloud-based operatorinterface system 502 and its associated cloud services.

Client interface component 512 can serve predesigned interface displays522 to any Internet-capable client device 520 (similar to client devices302 and 416 of FIGS. 3 and 4, respectively) having access privileges tothe cloud-based operator interface system 502, and render selectedsubsets of the industrial data via the display screens using the clientdevice's native display capabilities. To this end, a set ofpreconfigured display screens 508 can be stored on cloud storageassociated with the operator interface system 502, and the clientinterface component 512 can deliver selected display screens 508 inresponse to invocation by the client device 520. The display screens 508can be developed, for example, using a development environment providedby the cloud-based operator interface system 502. In one or moreembodiments, the cloud-based operator interface system 502 can providethis development environment as a cloud service, allowing a developer toremotely access a set of cloud-side interface screen development toolsto facilitate design of interface screen layouts, data links, graphicalanimations, and navigation links between screens. In such embodiments,the interface screen development environment can allow the developer toleverage cloud resources (e.g., cloud storage and processing resources)to develop a set of display screens 508 for a given operator interfaceapplication to be run on the operator interface system 502.Alternatively, some embodiments of the cloud-based operator interfacesystem 502 can allow display screens developed by external displaydevelopment applications to be uploaded to the cloud platform andexecuted by the operator interface system 502 during runtime.

Each of the display screens 508 can include display tags defining whichdata items are to be displayed on the respective screens, formats forthe respective data items, desired graphical animations to be associatedwith the respective data items, graphical elements to be included on therespective display screens (e.g., externally defined graphical elementsdefinitions), and other such configuration information. Some displayscreens 508 can also be configured to render alarm or informationalmessages in response to determinations that subsets of the industrialdata provided by cloud gateways 504 have met certain conditions (e.g.,in response to a determination that a given industrial parameter hasexceeded a defined setpoint, or that a defined production goal has beenmet). Since industrial data can be received from multiple industrialsystems (possibly at diverse geographical locations), alarms,notification events, animation triggers, and the like can be defined interms of composite industrial data values for multiple industrialsystems, allowing the industrial systems to be viewed and analyzed froma high-level enterprise perspective. For example, consider a scenario inwhich a particular product is being produced at three differentfacilities (e.g., locations 1-3 of FIG. 5). The respective cloudgateways 504 can deliver production statistics to the gateway interfacecomponent 524, and the operator interface system 502 can aggregate theseproduction statistics substantially in real-time to yield composite data(e.g., a total production count for all three facilities) even thoughthe three facilities may not be communicatively networked together overa data network. One or more of the displays screens 508 can beconfigured to display these composite production statistics, triggeralarms or graphical animations as a function of the compositestatistics, etc. Client interface component 512 can deliver thesedisplay screens to an authorized client device 520 having Internetaccess and suitable authorization credentials, providing an owner of theclient device 502 with an enterprise-level view of the multipleindustrial systems monitored by the operator interface system 502.

The cloud-based operator interface system 502 can support conditionaldisplay of industrial data based on defined user roles having differentlevels of access privileges. Accordingly, the operator interface system502 can allow multiple user roles to be defined (e.g., operator, plantmanager, finance, accounting, administrator, etc.), and customize thepresentation of industrial data for the respective user roles. Forexample, an administrator can associate a given user role with a subsetof display screens 508 that users belonging to that user role areallowed to access. In another example, selected data displays on thedisplay screens 508 can be configured with visibility links that renderthe selected data visible only to users associated with certainauthorized user roles.

In order to provide support for user-specific customization, cloud-basedoperator interface system 502 can maintain a set of user profiles 510corresponding to respective users of the system. An exemplary userprofile can include such information as a user identifier, one or moreuser roles to which the user belongs, and any user-defined preferencesconfigured by the user. For example, some user roles may be givenpermission to customize certain presentation aspects of the displayscreens 508 from their client device (e.g., alter an arrangement of dataitems on the screen, customize colors, render selected data valvesinvisible, etc.). When a user having such permissions customizes suchpresentation aspects at the client device 520, the operator interfacesystem 502 can save these preferences to the user's profile. When theuser subsequently invokes the customized display screen, the clientinterface component 512 will access the user's profile and apply thepreviously defined customization settings to the display screen prior toserving the display screen to the client device 520.

In a related aspect, one or more embodiments of the cloud-based operatorinterface system 502 can allow individual users to subscribe to selectedreal-time data feeds from one or more industrial systems. For example, amaintenance engineer may be interested in monitoring a particularperformance metric of a specific machine at a plant facility. Theoperator interface system 502 can allow the engineer to identify themachine and the performance metric (e.g., a temperature of a die castoven) and add this data feed to one of the existing display screens 508as a user preference. Alternatively, the operator interface system 502can create a new custom screen in response to the subscription request.In either case, the subscription information can be stored in theengineer's user profile, and the client interface component 512 canrender a live feed of the selected performance metric to the engineer'sclient device 520 upon request.

Since the operator interface displays can be served to diverse types ofclient devices (e.g., desktop computers, mobile phones, tabletcomputers, laptop computers, HMI terminals, television monitors, etc.),the cloud-based operator interface system 502 can render a given displayscreen in a format suitable for display on the device invoking thescreen, and in a manner that makes efficient use of the device'sresources. For example, if the operator interface system 502 receives arequest for a display screen from a cellular phone, the client interfacecomponent 512 can deliver the requested display screen to the cellularphone in a format adapted to the display capabilities of the phone(e.g., at a display ratio and resolution suitable for display on thephone's screen).

One or more embodiments of the cloud-based operator interface system canalso support delivery of multimedia presentations to client device 520.For example, in addition to presentation of production data retrievedfrom industrial controllers, users may wish to view a live video oraudio-video feed of an industrial process. Accordingly, cloud gateways504 can deliver live video or audio-video stream information (e.g., froma web camera) to the gateway interface component 524, and the clientinterface component 512 can deliver this video stream to client device520 in response to a request from the client device 520. In suchembodiments, the operator interface system 502 can be configured tooverlay selected subsets of live industrial data (also received from thecloud gateways 504) on the video to yield a composite presentation ofthe system.

In addition to delivery of industrial data from the cloud gateways 504,one or more embodiments of the cloud-based operator interface system 502can also support two-way data exchange, allowing users to send data orissue commands to industrial systems remotely from a client device 520via the cloud platform. For example, an operator may interact withinterface display 522 (rendered on client device 520 by the operatorinterface system 502) to enter a new setpoint value for a selectedmachine at a remote automation system (e.g., via a data field providedon the operator interface screen). The client device 520 can send thenew setpoint value to the cloud-based operator interface system viaclient interface component 512. The gateway interface component 524 candeliver this new setpoint value to a controller associated with theselected machine via the appropriate cloud gateway 504. The cloudgateway 504 can write the new setpoint value to the appropriatecontroller data tag or register, thereby implementing the new setpoint.In a similar manner, the cloud-based operator interface system 502 canallow single-bit commands to be issued from the client device 520, suchas start/stop commands issued via a graphical pushbutton rendered on theinterface display 522.

In order to enhance the value of received industrial data and providegreater depth for analysis, one or more embodiments of the cloud-basedoperator interface system 502 can add context to the data received bythe cloud gateways 504. To this end, context component 514 can appendcontextual metadata to selected subsets of the industrial data as it isreceived by the cloud gateways 504, thereby providing useful contextinformation for the industrial data that can be leveraged by theoperator interface system 502 in connection with cloud-side analysis toenhance the user's understanding of the monitored industrial systems.

Turning briefly to FIG. 6, an exemplary context component fortransforming raw industrial data into contextualized data isillustrated. Context component 604 (similar to context component 514 ofFIG. 5) receives raw industrial data 602 (e.g., from cloud gateways 504of FIG. 5), and enhances the raw data 602 with one or more pieces ofcontext data to yield contextualized data 606. For example, contextcomponent 604 can apply a time stamp to the raw data 602 indicating atime, a date, and/or a production shift when the data was generated. Theapplied context data may also include a production area or plantfacility that yielded the data, a particular product that was beingproduced when the data was generated, a state of a machine (e.g., auto,semi-auto, abnormal, etc.) at the time the data was generated, ageographical location of the data source (in the case of mobile controland/or monitoring systems, where such geographical location informationcan be received from a GPS device associated with the mobile system),etc. Other examples of context information include an employee on shiftat the time the data was generated, a lot number with which the data isassociated, or an alarm that was active at the time the data wasgenerated. Context component 604 can also apply an actionable data tagto the raw data if it is determined that the data requires action to betaken by plant personnel or by another cloud-based application.

Context component 604 can also apply contextual information to the rawdata 602 that reflects the data's location within a hierarchicalorganizational model. Such an organization model can represent anindustrial enterprise in terms of multiple hierarchical levels. In anexemplary organizational model, the hierarchical levels can include—fromlowest to highest—a workcell level, a line level, an area level, a sitelevel, and an enterprise level. Devices that are components of a givenautomation system can be described and identified in terms of thesehierarchical levels, allowing a common terminology to be used across theentire enterprise to identify devices, machines, and data within theenterprise. In some embodiments, the organizational model can be knownto the context component 604, which can stamp the raw data 602 with ahierarchical identification tag that indicates the data's origin withinthe organizational hierarchy (e.g.,Company:Marysville:DieCastArea:#1Headline:LeakTestCell).

Returning now to FIG. 5, some embodiments of the cloud-based operatorinterface system 502 can also include cloud-side analysis tools, whichallow the received industrial data to be correlated and analyzed on thecloud platform. In particular, an analytics component 516 (similar toanalytics component 210 of FIG. 2) can analyze subsets of the industrialdata received from the cloud gateways 504 according to predefined usercriteria. In an exemplary application, an administrator or other userwith appropriate administrative rights can specify that productionstatistics from production lines at multiple geographically diversefacilities are to be aggregated, and a notification is to be sent toselected users when these aggregated production statistics exceed adefined setpoint (e.g., when a total production count of all productionlines reaches a defined goal). Accordingly, analytics component 516 canaggregate the indicated production statistics substantially in real-timeas the industrial data is received by the respective cloud gateways 504,and monitor these aggregated statistics to determine when the aggregatenumbers meet the defined trigger event. When the analytics component 516determines that the production goal has been met, it can instruct theclient interface component 512 to deliver an indication (e.g., a messageor graphical animation on a display screen, a text message, etc.) to oneor more client devices associated with the relevant personnel.

Analytics component 516 can also be configured to analyze the incomingindustrial data to identify short-term or long-term trends that may beof interest to users. For example, an administrator can configure theoperator interface system 502 to store selected subsets of theindustrial data (or aggregates thereof) in cloud storage 506, andconfigure the analytics component 516 to identify possible correlationsbetween two sets of the stored data. In this regard, the analyticscomponent 516 can leverage the contextual metadata added by the contextcomponent 514 to facilitate robust analysis of the industrial data. Forexample, the analytics component 516 may identify that a particularindustrial machine runs less efficiently during certain work shifts ortimes of day, based on the received industrial data as well as date/timestamps or work shift identifiers applied to the data by the contextcomponent 514. The analytics component 516 can also monitor theindustrial data to detect outliers or anomalies that may indicate eitherabnormal system operation or inaccurate data (e.g., a malfunctioningtelemetry device or sensor), and instruct the client interface component512 to deliver a suitable alert to the client device 520.

As mentioned above, one or more embodiments of the cloud-based operatorinterface system 502 can include notification services for notifyingrelevant personnel of a detected event. Accordingly, the cloud-basedoperator interface system can include a notification component 518(similar to notification component 212 of FIG. 2) configured to deliversuch notifications to the selected client devices according topredefined user preferences. FIG. 7 illustrates an exemplarynotification architecture according to one or more embodiments of thisdisclosure. In this example, one or more controlled processes 720 aremonitored and/or controlled by industrial device 714, which can be anindustrial controller, a sensor, a meter, a motor drive, or other suchdevice. Alternatively, industrial device 714 may be a separate device(e.g., a proxy device) that is not directly involved in monitoring orcontrolling the controlled process(es) 720, but instead collects processdata from industrial devices involved with controlling the controlledprocess(es) 720, and delivers this data to the cloud platform. In suchembodiments, industrial device 714 can be, for example, a firewall boxor other such network infrastructure device, a data collection server,or other suitable device capable of collecting or generating industrialdata and providing this data to the cloud platform.

Industrial device 714 collects industrial data from controlledprocess(es) 720, or generates process data internally based on monitoredconditions of the controlled process(es) 720. In the present example,the cloud-based operator interface system 702 running on the cloudplatform can include notification component 704 (similar to notificationcomponent 518 of FIG. 5), which can be configured to receive industrialdata 710 from a cloud gateway 712 associated with a customer's plantfloor equipment and to route notifications 706 to appropriate plantpersonnel in accordance with predefined notification criteria.

On the cloud platform, analytics component 722 (similar to analyticscomponent 516 of FIG. 5) can determine whether selected subsets of theindustrial data 710 (or aggregations thereof) meet one or morepredefined notification conditions. These can include such conditions asdetecting that a particular process value has exceeded a definedsetpoint, detecting a transition to a particular machine state,detecting an alarm condition, determining that a specified productiongoal has been achieved, or other such conditions that can be detectedthrough analysis of the industrial data 710. When the analyticscomponent 722 detects an actionable condition within the industrial data710, analytics component 722 can inform the notification component 704that personnel are to be notified. In response, the notificationcomponent 704 can identify one or more specific plant employees who areto receive the notification, as well as information identifying a usernotification device, phone number, or email address for each person tobe notified.

In one or more embodiments, the notification component 704 can determinethis notification information by cross-referencing a configuration data724 that identifies which personnel are to be notified for a given typeof condition, one or more notification methods for each identifiedperson, and/or other relevant information. When analytics component 722determines that a subset of the industrial data 710 requires action tobe taken by plant personnel, notification component 704 can referenceconfiguration data 724 to determine, for example, which personnel shouldbe notified, which user devices should receive the notification, arequired action to be taken by the recipient, a due date for the action,a format for the notification, and/or other relevant information.Configuration data 724 can maintain multiple separate personnel listsrespectively associated with different types of actionable situations.In some embodiments, the personnel list selected for a givennotification can be at least partly a function of the context dataappended by context component 514. For example, if industrial data 710indicates that a process parameter has exceeded a setpoint value, thenotification component 704 can identify the list of personnel to receivethe notification based on the area or workcell to which the processparameter relates.

Once the notification component 704 had determined the appropriatepersonnel and devices to be notified, the notification component 704 candeliver notifications 706 to one or more notification destinations. Thenotification can be sent to one or more identified Internet-capableclient devices 708, such as a phone, a tablet computer, a desktopcomputer, or other suitable devices. In some embodiments, a cloudapplication running on the cloud platform can provide a mechanism fornotified personnel to communicate with one another via the cloud (e.g.,establish a conference call using Voice-over-IP). In some embodiments,the notification component 704 can be configured to send thenotification 706 periodically at a defined frequency until the userpositively responds to the notification (e.g., by sending a manualacknowledgement via the client device 708). The notification component704 can also be configured to escalate an urgency of high-prioritynotifications if an acknowledgment is not received within apredetermined amount of time. This urgency escalation can entail sendingthe notification 706 at a gradually increasing frequency, sending thenotification to devices associated with secondary personnel if theprimary personnel do not respond within a defined time period, or othersuch escalation measures.

FIGS. 8-10 illustrate various methodologies in accordance with one ormore embodiments of the subject application. While, for purposes ofsimplicity of explanation, the one or more methodologies shown hereinare shown and described as a series of acts, it is to be understood andappreciated that the subject innovation is not limited by the order ofacts, as some acts may, in accordance therewith, occur in a differentorder and/or concurrently with other acts from that shown and describedherein. For example, those skilled in the art will understand andappreciate that a methodology could alternatively be represented as aseries of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with the innovation. Furthermore, interactiondiagram(s) may represent methodologies, or methods, in accordance withthe subject disclosure when disparate entities enact disparate portionsof the methodologies. Further yet, two or more of the disclosed examplemethods can be implemented in combination with each other, to accomplishone or more features or advantages described herein.

FIG. 8 illustrates an example methodology 800 for viewing andcontrolling one or more industrial systems through a cloud platform.Initially, at 802, industrial data is received at an operator interfacesystem residing on a cloud platform. In one or more embodiments, theoperator interface system can comprise a cloud service available tousers (e.g., businesses, industrial enterprises, etc.) as a subscriptionservice, and which utilizes cloud storage and processing resources toimplement operator interface systems (e.g., HMIs, graphic terminals,message displays, industrial monitors etc.) capable of delivering anenterprise-level view of one or more industrial systems toInternet-capable client devices having suitable access privileges. Theindustrial data can be received at the operator interface system, forexample from one or more cloud gateways (e.g., cloud gateways 310, 404,and 504 of FIGS. 3, 4, and 5, respectively).

Optionally, at 804, the industrial data can be at least one ofcontextualized, filtered, or aggregated on the cloud platform by theoperator interface system. For example, the cloud-based operatorinterface can enhance some or all of the industrial data with contextualmetadata that provides a context for the data, such as a time/datestamp; a geographic location, production area, or machine from which thedata was received, a state of a process at the time the data wasgenerated on the plant floor, identifications of plant personnel on dutyat the time the data was generated, or other such contextualinformation. Related sets of data can also be aggregated (for example,production data from geographically diverse industrial facilitiesmanufacturing a common product), or filtered to remove redundant data.

At 806, one or more operator interface screens are generated by thecloud-based operator interface system for rendering a selected subset ofthe industrial data. The operator interface screens can comprisepre-developed display screens stored on a subset of the cloud platform'sstorage resources, and which can be invoked by the remote client devicesthrough the Internet. At 808, the one or more operator interface screensare delivered to an Internet-capable client device. In one or moreembodiments, the cloud-based operator interface system can tailor theone or more operator interface screens to adapt to the particulardisplay capabilities of the client device, based on a determination of atype of device being served (e.g., mobile phone with limited displaycapabilities, a desktop computer, a tablet computer, etc.). At 810, atleast a subset of the industrial data is rendered on the client devicevia the one or more operator interface screens.

FIG. 9 illustrates an example methodology 900 for deliveringnotifications of industrial events through a cloud platform. Initially,at 902, industrial data is received at an operator interface systemrunning as a service on a cloud platform (e.g., from cloud gateways 310,404, or 504 of FIGS. 3, 4, and 5, respectively). Optionally, at 904, theindustrial data can be at least one of contextualized, filtered, oraggregated on the cloud platform by the operator interface system, asdescribed in previous examples. At 906, a determination can be maderegarding whether a subset of the industrial data meets a predefinednotification condition. The notification condition can comprise, forexample, a determination that a particular process value has exceeded adefined setpoint, detection that a machine has transitioned to aparticular machine state, detection of an alarm condition, adetermination that a specified production goal has been achieved, orother such conditions that can be detected through analysis of theindustrial data.

If it is determined at 908 that the notification condition has been met,the methodology moves to step 910, where a determination is maderegarding which users of the operator interface system are to benotified. The operator interface system can make this determination, forexample, by referencing configuration data that identifies whichpersonnel are to be notified for a given type of system condition, oneor more notification methods for each identified person, and/or othersuch information. At 912, a notification is delivered from the cloudplatform to the devices associated with the users identified at step910. The notification can be sent to any suitable Internet-capableclient device, such as a phone, a tablet computer, a desktop computer,or other such devices. It is to be appreciated that steps 902-906 maycontinue to be performed while notification steps 910 and 912 areexecuting, as new industrial data is received at the operator interfacesystem.

FIG. 10 illustrates an example methodology 1000 for delivering operatorinterface screens to Internet-capable client devices from a cloudplatform. Initially, at 1002, a set of operator interface screens arestored on cloud storage associated with a cloud-based operator interfacesystem. These display screens can be developed, for example, using acloud-based display screen development service that allows a developerto leverage cloud resources in connection with developing the set ofoperator interface screens. Alternatively, the operator interfacescreens can be developed locally at a user workstation and uploaded tothe cloud platform for storage by the cloud-based operator interfacesystem.

At 1004, automation data generated by an industrial automation system isreceived at the cloud-based operator interface system. The data can bereceive, for example, by a cloud gateway that reads the automation datafrom an industrial controller and pushes the data to the cloud platformfor use by the cloud-based operator interface system. At 1006, a requestfor one of the stored operator interface screens is received from aclient device over the Internet. In response to receiving the request,at 1008, a user profile associated with the client device is access todetermine whether any previously stored display preferences are to beapplied to the requested operator interface screen prior to delivery.For example, a user of the client device may have customized one or moreaspects of the requested operator interface screen during a previousviewing. These customized aspects can be stored in the user profileassociated with the client device so that the cloud-based operatorinterface system can apply the user's preferences the next time thescreen is invoked by the client device. In this manner, a common set ofoperator interface screens can be stored on the cloud platform andserved to multiple users in accordance with respective user displaypreferences.

If it is determined at 1010 that the user profile specifies a displaypreference, the display preference is applied to the operator interfacescreen at 1012. At 1014, the requested operator interface screen isdelivered to the client device over the Internet. If it is determined at1010 that no display preferences are to be applied, the methodologymoves directly to step 1014 without applying a display preference at1012. At 1016, a live feed of a subset of the automation data isdelivered to the client device via the requested operator interfacescreen.

Embodiments, systems, and components described herein, as well asindustrial control systems and industrial automation environments inwhich various aspects set forth in the subject specification can becarried out, can include computer or network components such as servers,clients, programmable logic controllers (PLCs), automation controllers,communications modules, mobile computers, wireless components, controlcomponents and so forth which are capable of interacting across anetwork. Computers and servers include one or more processors—electronicintegrated circuits that perform logic operations employing electricsignals—configured to execute instructions stored in media such asrandom access memory (RAM), read only memory (ROM), a hard drives, aswell as removable memory devices, which can include memory sticks,memory cards, flash drives, external hard drives, and so on.

Similarly, the term PLC or automation controller as used herein caninclude functionality that can be shared across multiple components,systems, and/or networks. As an example, one or more PLCs or automationcontrollers can communicate and cooperate with various network devicesacross the network. This can include substantially any type of control,communications module, computer, Input/Output (I/O) device, sensor,actuator, and human machine interface (HMI) that communicate via thenetwork, which includes control, automation, and/or public networks. ThePLC or automation controller can also communicate to and control variousother devices such as I/O modules including analog, digital,programmed/intelligent I/O modules, other programmable controllers,communications modules, sensors, actuators, output devices, and thelike.

The network can include public networks such as the Internet, intranets,and automation networks such as control and information protocol (CIP)networks including DeviceNet, ControlNet, and Ethernet/IP. Othernetworks include Ethernet, DH/DH+, Remote I/O, Fieldbus, Modbus,Profibus, CAN, wireless networks, serial protocols, and so forth. Inaddition, the network devices can include various possibilities(hardware and/or software components). These include components such asswitches with virtual local area network (VLAN) capability, LANs, WANs,proxies, gateways, routers, firewalls, virtual private network (VPN)devices, servers, clients, computers, configuration tools, monitoringtools, and/or other devices.

In order to provide a context for the various aspects of the disclosedsubject matter, FIGS. 11 and 12 as well as the following discussion areintended to provide a brief, general description of a suitableenvironment in which the various aspects of the disclosed subject mattermay be implemented.

With reference to FIG. 11, an example environment 1110 for implementingvarious aspects of the aforementioned subject matter includes a computer1112. The computer 1112 includes a processing unit 1114, a system memory1116, and a system bus 1118. The system bus 1118 couples systemcomponents including, but not limited to, the system memory 1116 to theprocessing unit 1114. The processing unit 1114 can be any of variousavailable processors. Dual microprocessors and other multiprocessorarchitectures also can be employed as the processing unit 1114.

The system bus 1118 can be any of several types of bus structure(s)including the memory bus or memory controller, a peripheral bus orexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, 8-bit bus, IndustrialStandard Architecture (ISA), Micro-Channel Architecture (MSA), ExtendedISA (EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB),Peripheral Component Interconnect (PCI), Universal Serial Bus (USB),Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), and Small Computer SystemsInterface (SCSI).

The system memory 1116 includes volatile memory 1120 and nonvolatilememory 1122. The basic input/output system (BIOS), containing the basicroutines to transfer information between elements within the computer1112, such as during start-up, is stored in nonvolatile memory 1122. Byway of illustration, and not limitation, nonvolatile memory 1122 caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable PROM (EEPROM), or flashmemory. Volatile memory 1120 includes random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM).

Computer 1112 also includes removable/non-removable,volatile/nonvolatile computer storage media. FIG. 11 illustrates, forexample a disk storage 1124. Disk storage 1124 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, Jaz drive, Zip drive, LS-100 drive, flash memory card, or memorystick. In addition, disk storage 1124 can include storage mediaseparately or in combination with other storage media including, but notlimited to, an optical disk drive such as a compact disk ROM device(CD-ROM), CD recordable drive (CD-R Drive), CD rewritable drive (CD-RWDrive) or a digital versatile disk ROM drive (DVD-ROM). To facilitateconnection of the disk storage devices 1124 to the system bus 1118, aremovable or non-removable interface is typically used such as interface1126.

It is to be appreciated that FIG. 11 describes software that acts as anintermediary between users and the basic computer resources described insuitable operating environment 1110. Such software includes an operatingsystem 1128. Operating system 1128, which can be stored on disk storage1124, acts to control and allocate resources of the computer system1112. System applications 1130 take advantage of the management ofresources by operating system 1128 through program modules 1132 andprogram data 1134 stored either in system memory 1116 or on disk storage1124. It is to be appreciated that one or more embodiments of thesubject disclosure can be implemented with various operating systems orcombinations of operating systems.

A user enters commands or information into the computer 1112 throughinput device(s) 1136. Input devices 1136 include, but are not limitedto, a pointing device such as a mouse, trackball, stylus, touch pad,keyboard, microphone, joystick, game pad, satellite dish, scanner, TVtuner card, digital camera, digital video camera, web camera, and thelike. These and other input devices connect to the processing unit 1114through the system bus 1118 via interface port(s) 1138. Interfaceport(s) 1138 include, for example, a serial port, a parallel port, agame port, and a universal serial bus (USB). Output device(s) 1140 usesome of the same type of ports as input device(s) 1136. Thus, forexample, a USB port may be used to provide input to computer 1112, andto output information from computer 1112 to an output device 1140.Output adapter 1142 is provided to illustrate that there are some outputdevices 1140 like monitors, speakers, and printers, among other outputdevices 1140, which require special adapters. The output adapters 1142include, by way of illustration and not limitation, video and soundcards that provide a means of connection between the output device 1140and the system bus 1118. It should be noted that other devices and/orsystems of devices provide both input and output capabilities such asremote computer(s) 1144.

Computer 1112 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1144. The remote computer(s) 1144 can be a personal computer, a server,a router, a network PC, a workstation, a microprocessor based appliance,a peer device or other common network node and the like, and typicallyincludes many or all of the elements described relative to computer1112. For purposes of brevity, only a memory storage device 1146 isillustrated with remote computer(s) 1144. Remote computer(s) 1144 islogically connected to computer 1112 through a network interface 1148and then physically connected via communication connection 1150. Networkinterface 1148 encompasses communication networks such as local-areanetworks (LAN) and wide-area networks (WAN). LAN technologies includeFiber Distributed Data Interface (I-DDI), Copper Distributed DataInterface (CDDI), Ethernet/IEEE 802.3, Token Ring/IEEE 802.5 and thelike. WAN technologies include, but are not limited to, point-to-pointlinks, circuit switching networks like Integrated Services DigitalNetworks (ISDN) and variations thereon, packet switching networks, andDigital Subscriber Lines (DSL).

Communication connection(s) 1150 refers to the hardware/softwareemployed to connect the network interface 1148 to the bus 1118. Whilecommunication connection 1150 is shown for illustrative clarity insidecomputer 1112, it can also be external to computer 1112. Thehardware/software necessary for connection to the network interface 1148includes, for exemplary purposes only, internal and externaltechnologies such as, modems including regular telephone grade modems,cable modems and DSL modems, ISDN adapters, and Ethernet cards.

FIG. 12 is a schematic block diagram of a sample-computing environment1200 with which the disclosed subject matter can interact. The system1200 includes one or more client(s) 1202. The client(s) 1202 can behardware and/or software (e.g., threads, processes, computing devices).The system 1200 also includes one or more server(s) 1204. The server(s)1204 can also be hardware and/or software (e.g., threads, processes,computing devices). The servers 1204 can house threads to performtransformations by employing one or more embodiments as describedherein, for example. One possible communication between a client 1202and servers 1204 can be in the form of a data packet adapted to betransmitted between two or more computer processes. The system 1200includes a communication framework 1205 that can be employed tofacilitate communications between the client(s) 1202 and the server(s)1204. The client(s) 1202 are operably connected to one or more clientdata store(s) 1208 that can be employed to store information local tothe client(s) 1202. Similarly, the server(s) 1204 are operably connectedto one or more server data store(s) 1210 that can be employed to storeinformation local to the servers 1204.

What has been described above includes examples of the subjectinnovation. It is, of course, not possible to describe every conceivablecombination of components or methodologies for purposes of describingthe disclosed subject matter, but one of ordinary skill in the art mayrecognize that many further combinations and permutations of the subjectinnovation are possible. Accordingly, the disclosed subject matter isintended to embrace all such alterations, modifications, and variationsthat fall within the spirit and scope of the appended claims.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated exemplary aspects of the disclosed subjectmatter. In this regard, it will also be recognized that the disclosedsubject matter includes a system as well as a computer-readable mediumhaving computer-executable instructions for performing the acts and/orevents of the various methods of the disclosed subject matter.

In addition, while a particular feature of the disclosed subject mattermay have been disclosed with respect to only one of severalimplementations, such feature may be combined with one or more otherfeatures of the other implementations as may be desired and advantageousfor any given or particular application. Furthermore, to the extent thatthe terms “includes,” and “including” and variants thereof are used ineither the detailed description or the claims, these terms are intendedto be inclusive in a manner similar to the term “comprising.”

In this application, the word “exemplary” is used to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion.

Various aspects or features described herein may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks [e.g., compact disk (CD), digital versatile disk (DVD) . . . ],smart cards, and flash memory devices (e.g., card, stick, key drive . .. ).

What is claimed is:
 1. A system that provides operator interfaceservices using a cloud platform, comprising: a memory; and a processorthat executes computer-executable components stored on the memory toimplement the system, the computer-executable components comprising: agateway interface component configured to receive industrial data froman industrial system, wherein the gateway interface receives theindustrial data on a cloud platform; a context component configured toadd contextual metadata to at least a subset of the industrial data,wherein the contextual metadata comprises at least a hierarchical tagthat identifies an origin of the subset of the industrial data within anindustrial enterprise in terms of two or more hierarchical levels of theindustrial enterprise, the two or more hierarchical levels comprising atleast one of a plant facility or a production area within the plantfacility that yielded the data; a state of a machine of the industrialsystem at a time that the subset of the industrial data was generated;and in response to determining that the subset of the industrial datarequires an action to be taken by plant personnel, an actionable datatag; and a client interface component configured to send the subset ofthe industrial data from the cloud platform to a client device andrender the subset of the industrial data on the client device based onthe contextual metadata.
 2. The system of claim 1, wherein the clientinterface component is configured to select the subset of the industrialdata for delivery to the client device based on a defined role of a userassociated with the client device.
 3. The system of claim 1, wherein theclient interface component is further configured to: receive, viainteraction with the client device, an identity of a machine of theindustrial system, and based on the identity of the machine, sendanother subset of the industrial data corresponding to a performancemetric of the machine from the cloud platform to the client device. 4.The system of claim 1, wherein the gateway interface component isconfigured to receive multiple sets of industrial data, including theindustrial data, from respective different industrial facilities and toaggregate the multiple sets of industrial data to yield aggregatedindustrial data, and the system further comprises a notificationcomponent configured to send, to the client device, a notification inresponse to a determination that the aggregated industrial datasatisfies a defined criterion.
 5. The system of claim 4, wherein thedefined criterion is a requirement that a production count representedby the aggregated industrial data reaches a defined production countgoal.
 6. The system of claim 4, wherein the notification component isconfigured to determine one or more recipients for the notificationbased on configuration data that associates the one or more recipientswith a type of condition indicated by the aggregated industrial data. 7.The system of claim 6, wherein the notification component is furtherconfigured to include, in the notification, an action required to betaken by the one or more recipients and a due date for the action. 8.The system of claim 1, wherein the contextual metadata further comprisesa plant employee identifier representing an identity of an employee onshift at a time that the subset of the industrial data was generated. 9.The system of claim 1, wherein the memory comprises cloud storage thatstores a plurality of display screens, and the client interfacecomponent is configured to serve one or more of the display screens tothe client device and to deliver at least the subset of the industrialdata via the one or more of the display screens.
 10. The system of claim9, wherein the memory comprises cloud storage that stores user profiledata that defines at least one of access privileges or preferences forrespective users, and the client interface component is furtherconfigured to control delivery of at least the subset of the industrialdata based on the user profile data.
 11. The system of claim 10, whereinthe client interface component is further configured to receivecustomization input, from the client device, that specifies a displaypreference for the one or more display screens, and store thecustomization input in a user profile, defined by the user profile data,corresponding to the client device.
 12. A method for deliveringindustrial data, comprising: receiving, by a cloud-based systemcomprising at least one processor, industrial data from one or moreautomation systems; appending, by the cloud-based system, contextualinformation to at least a subset of the industrial data, wherein theappending comprises: appending a hierarchical tag to the subset of theindustrial data that identifies an origin of the subset of theindustrial data within an industrial enterprise in terms of at least twohierarchical levels of the industrial enterprise, the at least twohierarchical levels comprising at least one of a plant facilityidentifier or a production area identifier; appending an indication of astate of a machine of the one or more automation systems at a time thatthe subset of the industrial data was generated; and in response todetermining that the subset of the industrial data requires an action tobe taken by plant personnel, appending an actionable data tag to thesubset of the industrial data; serving, by the cloud-based system, anoperator interface screen to a client device from the cloud platform inresponse to receiving a request from the client device for the subset ofthe industrial data; and displaying, by the cloud-based system, thesubset of the industrial data on the client device via the operatorinterface screen in accordance with the contextual information.
 13. Themethod of claim 12, wherein the receiving the industrial data comprises:receiving multiple sets of industrial data, including the industrialdata, from respective different industrial facilities, and aggregatingthe multiple sets of industrial data to yield aggregated industrialdata, and the method further comprises: in response to determining thatthe aggregated industrial data satisfies a defined criterion, sending,by the cloud-based system, notification data to the client device. 14.The method of claim 13, wherein the determining that the aggregatedindustrial data satisfies the defined criterion comprises determiningthat a production count represented by the aggregated industrial dataachieves a defined production count goal.
 15. The method of claim 12,wherein the sending the notification data comprises determining arecipient for the notification data based on a referencing ofconfiguration data that associates the recipient with a type ofcondition indicated by the aggregated industrial data.
 16. The method ofclaim 15, wherein the sending the notification data comprises sending,as part of the notification data, information identifying an actionrequired to be taken by the recipient and a due date for the action. 17.The method of claim 12, wherein the appending further comprisesappending a plant employee identifier to the subset of industrial data,the plant employee identifier representing an identity of an employee onshift at a time that the subset of the industrial data was generated.18. The method of claim 12, wherein the displaying comprises: storing,on storage associated with the cloud-based system, a plurality ofdisplay screens, serving one or more of the display screens to theclient device, and delivering the subset of the industrial data via theone or more of the display screens.
 19. A non-transitorycomputer-readable medium having stored thereon executable instructionsthat, in response to execution, cause a computing system to performoperations, the operations comprising: interfacing with a cloud gatewayassociated with an industrial system; receiving industrial data relatingto the industrial system from the cloud gateway; adding contextualinformation to the industrial data, wherein the adding comprises: addinga hierarchical tag to the industrial data that identifies an origin ofthe industrial data within an industrial enterprise in terms of two ormore hierarchical levels of the industrial enterprise, the two or morehierarchical levels comprising at least one of a plant facility or aproduction area that generated the industrial data; adding an indicationof a state of a machine of the industrial system at a time that theindustrial data was generated; and in response to determining that theindustrial data indicates that an action is to be taken by plantpersonnel, adding an actionable data tag to the industrial data;interfacing with a client device over an Internet layer; and renderingthe industrial data on the client device over the Internet layer basedon the contextual metadata.
 20. The non-transitory computer-readablemedium of claim 19, wherein the receiving the industrial data comprises:receiving multiple sets of industrial data, including the industrialdata, from respective different industrial facilities, and aggregatingthe multiple sets of industrial data to yield aggregated industrialdata, and the operations further comprise: in response to determiningthat the aggregated industrial data satisfies a defined criterion,sending notification data to the client device.